QuickOPC.NET and QuickOPC-UA allows you to easily store objects (and object graphs, i.e. interconnected objects) into files and streams, and also to load them back.

Two types of serialization are supported:

• Basic serialization using Serializable attribute and/or ISerializable interface. This serialization type is typically used with BinaryFormatter for storing objects in a binary format.
• XML serialization using XmlSerializer and IXmlSerializable. This serialization provides objects storage in XML format.

Practically all QuickOPC objects (and their collections and dictionaries) can be serialized and deserialized. For example:

• You can load and store EasyDAClient, EasyAEClient and EasyUAClient objects (their instance properties, i.e. various parameters, are serialized).
• You can load and store parameter objects, such as DAGroupParameters.
• You can load and store arguments (and arrays of arguments) passed to functions, such as lists of items to be subscribed to (DAItemGroupArguments). This functionality can be used e.g. with storing lists of subscribed items in file, outside your application code.
• You can load and store results of browsing and querying (e.g. DANodeElementCollection, AECategoryElementCollection, and UANodeElementCollection).
• You can load and store results of reading (e.g. DAVtq, or UAAttributeData).
• You can load and store condition states (AEConditionState) and event data (AEEventData).
• You can load and store all notification data contained in event arguments, for OPC Data Access item changes (EasyDAItemChangedEventArgs), OPC Alarms and Events notifications (EasyAENotificationEventArgs), or OPC Unified Architecture monitored item changes (EasyUADataChangeNotificationEventArgs). This functionality can be used e.g. for easy logging of significant changes and events in the underlying system.